Mark several privacy sandbox features as discouraged#3526
Mark several privacy sandbox features as discouraged#3526captainbrosset merged 12 commits intoweb-platform-dx:mainfrom
Conversation
7957bb3 to
e5ff69e
Compare
e5ff69e to
3276862
Compare
| export function convertMarkdown(markdown: string) { | ||
| export function convertMarkdown(markdown: unknown) { | ||
| if (typeof markdown !== "string") { | ||
| throw new Error(`${markdown} is not a string!`); | ||
| } | ||
|
|
||
| const mdTree = unified().use(remarkParse).parse(markdown); |
There was a problem hiding this comment.
Remark stringifies anything, apparently, converting undefined to the string "undefined". This throw ought to stop us from "successfully" converting missing fields to strings.
|
This is becoming more urgent as BCD has started marking the keys as deprecated: |
3426b70 to
c7e9327
Compare
captainbrosset
left a comment
There was a problem hiding this comment.
@foolip could someone from Google please review this PR?
|
For info, the Privacy Sandbox status page proved a useful resource to find up to date information on this: https://privacysandbox.google.com/overview/status |
captainbrosset
left a comment
There was a problem hiding this comment.
Making some suggestions as per Sam's review.
captainbrosset
left a comment
There was a problem hiding this comment.
More suggestions (this PR is from Daniel's fork, so I can't contribute to it directly).
Google is deprecating a number of privacy sandbox features I think all of them are single implementer, so they'll qualify for deprecation in BCD and end up here too. No reason not to get ahead a little. Features affected:
attribution-reportingprotected-audience(see Addprotected-audiencefeature #2635)storage-access(break outrequestStorageAccessFor())shared-storagetopicsThere are questions about Edge on some of these, so there's some more research to be done on this.
via mdn/browser-compat-data#28417, where there's a nice list of links to intent-to-deprecate messages.